Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1748

reference
870-tree-1
name
1748
tree-preservation-order

undefined

870-tpo-1
uprn
address-text
point
POINT (-1.038760 50.870600)
geometry
MULTIPOLYGON (((-1.038632 50.870587,-1.038638 50.870612,-1.038655 50.870635,-1.038683 50.870653,-1.038719 50.870664,-1.038758 50.870669,-1.038798 50.870665,-1.038834 50.870654,-1.038862 50.870636,-1.038881 50.870614,-1.038888 50.870589,-1.038882 50.870564,-1.038864 50.870541,-1.038836 50.870523,-1.038801 50.870511,-1.038762 50.870507,-1.038722 50.870511,-1.038686 50.870522,-1.038657 50.870539,-1.038639 50.870562,-1.038632 50.870587)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL